fix: set authenticatorAttachment to platform on iOS for passkey creation#2417
fix: set authenticatorAttachment to platform on iOS for passkey creation#2417
Conversation
Chrome iOS (with Google Password Manager) shows a 'Sign in' dialog instead of 'Create Passkey' when authenticatorAttachment is undefined. Explicitly setting it to 'platform' on iOS ensures the native overlay correctly prompts for passkey creation.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude finished @broody's task —— View job I'll analyze the controller repository changes and update the documentation in the docs-repo directory accordingly. Tasks:
Analysis:The PR fixes a Chrome iOS specific issue where Found relevant documentation files that mention passkeys/WebAuthn:
Conclusion:No documentation updates needed. This fix is an internal implementation improvement that resolves a Chrome iOS-specific passkey creation issue. It doesn't change:
The change maintains the existing passkey functionality while fixing a browser-specific bug, so current documentation remains accurate and complete. |
1 participant
Problem
On Chrome iOS, clicking "Create Passkey" in the popup triggers the native Apple passkey overlay to show a "Sign in with passkey" dialog instead of creating a new passkey. Safari iOS works fine.
Root Cause
Chrome iOS (with Google Password Manager integration since Chrome 136) interprets
authenticatorAttachment: undefineddifferently from Safari. When unset, Chrome iOS shows a sign-in dialog offering existing passkeys rather than directly creating a new one.Fix
Explicitly set
authenticatorAttachment: "platform"on iOS devices. This tells the browser we specifically want to create a new platform-bound passkey using Face ID/Touch ID, which triggers the correct "Create Passkey" flow on both Safari and Chrome iOS.